Skip to content

Remove agent names and version constraints in MCP server documentation#479

Merged
MervinPraison merged 1 commit intomainfrom
develop
May 15, 2025
Merged

Remove agent names and version constraints in MCP server documentation#479
MervinPraison merged 1 commit intomainfrom
develop

Conversation

@MervinPraison
Copy link
Copy Markdown
Owner

@MervinPraison MervinPraison commented May 15, 2025

Summary by CodeRabbit

  • Documentation
    • Updated installation instructions by removing explicit version constraints for package installation.
    • Simplified example code snippets by removing unnecessary parameters and clarifying usage.
    • Added new sections demonstrating both simple and advanced multi-agent MCP server setups.
    • Improved organization and clarity of documentation examples without altering underlying functionality.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented May 15, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The documentation for deploying and configuring MCP servers was updated. Explicit version constraints were removed from package installation commands. Example code snippets were reorganized and clarified: agent instantiations no longer include the name parameter, and new multi-agent server examples were added, including both simple and custom tool scenarios. No changes were made to code logic or public API declarations.

Changes

File(s) Change Summary
docs/deploy/mcp-server-deploy.mdx, docs/mcp/mcp-server.mdx Removed version constraints from installation commands; updated and expanded example code snippets to remove agent name parameters; reorganized and clarified multi-agent server examples, adding new simple and custom tool usage scenarios.

Poem

In the meadow where agents play,
Rabbits hop and code all day.
Names are gone, instructions stay—
Simpler paths to lead the way.
Multi-agent friends unite,
Sharing tools, their futures bright.
🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between ecc7fe1 and 110cbb4.

📒 Files selected for processing (2)
  • docs/deploy/mcp-server-deploy.mdx (4 hunks)
  • docs/mcp/mcp-server.mdx (5 hunks)

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@MervinPraison MervinPraison merged commit e86a676 into main May 15, 2025
3 of 7 checks passed
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @MervinPraison, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

Hello team, gemini-code-assist here to provide a summary of this pull request by @MervinPraison.

This PR focuses on updating the documentation for deploying and creating Model Context Protocol (MCP) servers. The primary changes involve removing specific version constraints for the praisonaiagents package in installation instructions and removing the explicit name parameter from Agent and Agents instantiation in the Python code examples provided in the documentation. Additionally, a new section is added to the mcp-server.mdx file to show a simpler multi-agent server setup without custom tools.

Highlights

  • Documentation Updates: The pull request updates two documentation files related to MCP servers (docs/deploy/mcp-server-deploy.mdx and docs/mcp/mcp-server.mdx).
  • Removed Version Constraints: Specific version constraints (e.g., >=0.0.81) have been removed from pip install commands for the praisonaiagents[mcp] package in the documentation, simplifying installation instructions.
  • Removed Agent/Agents Names: The name parameter is removed from the instantiation of Agent and Agents classes in the Python code examples within the documentation. This suggests that providing an explicit name might no longer be required or is being de-emphasized in these examples.
  • Added Simple Multi-Agent Example: A new section and code example for setting up a simple multi-agent MCP server without custom tools has been added to the docs/mcp/mcp-server.mdx file.

Changelog

Click here to see the changelog
  • docs/deploy/mcp-server-deploy.mdx
    • Removed version constraint >=0.0.81 from pip install "praisonaiagents[mcp]" commands (lines 18, 23).
    • Removed name="TweetAgent" from the single agent example (line 33).
    • Removed name="SearchAgent" and name="SummariseAgent" from the multi-agent example with custom tools (lines 55, 56).
    • Removed name="MultiAgents" from the Agents instantiation in the multi-agent example with custom tools (line 58).
    • Added a new section titled "Simple Multi-Agent MCP Server" with corresponding code examples (added around line 62).
    • Removed version constraint >=0.0.81 from the praisonaiagents[mcp] entry in the requirements.txt example (line 89).
  • docs/mcp/mcp-server.mdx
    • Changed the title from "Creating MCP Servers" to "MCP Servers" (line 2).
    • Removed name="TweetAgent" from the single agent example (line 28).
    • Removed version constraint >=0.0.81 from the pip install "praisonaiagents[mcp]" command (line 48).
    • Removed name="SearchAgent" and name="SummariseAgent" from the multi-agent example with custom tools (lines 68, 69).
    • Removed name="MultiAgents" from the Agents instantiation in the multi-agent example with custom tools (line 71).
    • Added a new section titled "Multi-Agent MCP Server (Simple)" with corresponding code examples (added around line 84).
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


Docs updated, clear and bright,
Names removed, a lighter sight.
Install now, no version fear,
MCP servers, drawing near.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@netlify
Copy link
Copy Markdown

netlify bot commented May 15, 2025

Deploy Preview for praisonai ready!

Name Link
🔨 Latest commit 110cbb4
🔍 Latest deploy log https://app.netlify.com/projects/praisonai/deploys/6825ca4926672900080f4b05
😎 Deploy Preview https://deploy-preview-479--praisonai.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request effectively simplifies the MCP server documentation by removing explicit version constraints for praisonaiagents in installation commands and by removing the optional name parameter from Agent and Agents instantiations in the examples. These changes make the documentation cleaner and encourage users to adopt the latest package versions.

The addition of a new "Simple Multi-Agent MCP Server" example in docs/mcp/mcp-server.mdx is a welcome improvement for clarity. However, there's a point of potential confusion in docs/deploy/mcp-server-deploy.mdx that needs addressing.

Summary of Findings

  • Documentation Clarity: A redundant code block was identified in docs/deploy/mcp-server-deploy.mdx, which could confuse users. This is detailed in a specific review comment.
  • Dependency Simplification: The removal of version constraints (e.g., >=0.0.81) from pip install praisonaiagents[mcp] commands is a good change, simplifying setup for users.
  • Example Code Simplification: Removing the optional name parameter from Agent and Agents initializations in the examples makes them cleaner and focuses on essential parameters.
  • New Example Addition: The new 'Simple Multi-Agent MCP Server' example in docs/mcp/mcp-server.mdx (and its intended counterpart in docs/deploy/mcp-server-deploy.mdx) is a valuable addition, showcasing a simpler multi-agent setup.
  • Minor Formatting Changes: Minor formatting changes, such as the removal of an extra blank line in docs/deploy/mcp-server-deploy.mdx and a title adjustment in docs/mcp/mcp-server.mdx, were noted. These are low severity and not individually commented on per review settings.

Merge Readiness

The pull request introduces several positive changes to the documentation. However, there is a high-severity issue regarding a potentially redundant code block in docs/deploy/mcp-server-deploy.mdx that should be addressed to ensure clarity. I recommend that this issue be resolved before merging. As an AI reviewer, I am not authorized to approve pull requests; please ensure further review and approval by authorized maintainers.

Comment on lines +74 to 94
```python
from praisonaiagents import Agent, Agents
from duckduckgo_search import DDGS

def internet_search_tool(query: str):
results = []
ddgs = DDGS()
for result in ddgs.text(keywords=query, max_results=5):
results.append({
"title": result.get("title", ""),
"url": result.get("href", ""),
"snippet": result.get("body", "")
})
return results

agent = Agent(instructions="You Search the internet for information", tools=[internet_search_tool])
agent2 = Agent(instructions="You Summarise the information")

agents = Agents(name="MultiAgents", agents=[agent, agent2])
agents = Agents(agents=[agent, agent2])
agents.launch(port=8080, host="0.0.0.0", protocol="mcp")
```
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

This code block (lines 74-94) appears to be identical to the 'Multi-Agent MCP Server with Custom Tools' example already present in this document (see lines 40-60).

Could you clarify if this duplication under the 'Simple Multi-Agent MCP Server' heading is intentional? If it's meant to illustrate something different, the surrounding explanation or the example itself might need adjustment. If it's redundant, removing it would help prevent potential confusion for users.

shaneholloman pushed a commit to shaneholloman/praisonai that referenced this pull request Feb 4, 2026
Remove agent names and version constraints in MCP server documentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant